MA0192 currently catches (value & Flag) == Flag style checks, but it misses the common zero-comparison form used to test bit presence. This makes the rule inconsistent and leaves valid HasFlag simplifications unreported.

What changed

• Extend MA0192 analyzer detection to support:
  • (value & Flag) == 0
  • (value & Flag) != 0
  • (value & Flag) is 0
  • (value & Flag) is not 0
• Keep existing same-flag patterns (== Flag, != Flag, is Flag, is not Flag).
• Restrict zero-based detections to single-bit enum members only (non-zero power-of-two values), so combined flags do not trigger diagnostics.
• Update the code fix logic to preserve correct semantics for zero comparisons (== 0/is 0 -> !HasFlag, != 0/is not 0 -> HasFlag).
• Add/extend tests for new positive and negative scenarios.
• Update MA0192 documentation to describe the new supported patterns and single-bit constraint.

Notes for reviewers

The main non-obvious behavior is the single-bit guard for zero comparisons. This is intentional to avoid changing meaning for combined flag constants where HasFlag and != 0 are not equivalent.